Skip to content

Conversation

@SpawnAtis
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Oct 31, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (c97b0f8) to head (1a11888).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##              main     #2585    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files          415       415            
  Lines        19994     20114   +120     
  Branches      3378      3399    +21     
==========================================
+ Hits         19994     20114   +120     
Flag Coverage Δ
unittests 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

const target = event.currentTarget as HTMLElement | null;

this._longPressTimeoutId = window.setTimeout(() => {
this._suppressNextClick = true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a problem if click is not fired, then the next button click will be ignored

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added a code to reset suppress flag after a delay to handle cases where click doesn't fire

return event;
}

it('tapping 0 adds "0"', async () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's follow our naming convention with 'should'

Suggested change
it('tapping 0 adds "0"', async () => {
it('should add "0" when tapping 0', async () => {

@pointerup="${(_, c) => c.parent._endLongPress()}"
@pointercancel="${(_, c) => c.parent._cancelLongPress()}"
@pointerleave="${(_, c) => c.parent._cancelLongPress()}"
@click="${onDigitClick}">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about long-pressing with the keyboard? It should probably long-press with space as well
Maybe it would be easier to track the time when the pointer or keyboard press started and determine in the click handler if it was a long press. Just note that pointer/keyup is fired before click

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For 'long-press with space' it should be handled by input, but not digit buttons. I have added the implementation

@SpawnAtis SpawnAtis force-pushed the VIV-2876-add-long-press-on-0-dial-pad branch from cde467e to b4a7501 Compare November 7, 2025 07:35
@SpawnAtis SpawnAtis force-pushed the VIV-2876-add-long-press-on-0-dial-pad branch from ec75401 to 1a11888 Compare November 10, 2025 12:18
@SpawnAtis SpawnAtis added this pull request to the merge queue Nov 11, 2025
Merged via the queue into main with commit feed143 Nov 11, 2025
22 of 23 checks passed
@SpawnAtis SpawnAtis deleted the VIV-2876-add-long-press-on-0-dial-pad branch November 11, 2025 08:15
@github-actions github-actions bot mentioned this pull request Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants